Basic implementation of Copy-On-Write #96
Conversation
|
Hi Alejandro, Would you mind adding a test that uses your extension so that it can be fully tested? |
|
I wouldn't mind, but I don't know how the test framework from PRoot works. I see files in the test directory, and I only see a bunch of files with test-XXXXX (which looks quite random to me). If you can point me to an specific example on how to plug in my test, I would be happy to write one. |
* upstream/master: Use LC_ALL instead of LANG fix: update URLs to proot-me.github.io add: gitignore Fix use of size
|
Changes Unknown when pulling 5342c87 on TortugaLabs:cow into ** on proot-me:master**. |
|
The travis logs give some commands to execute the tests: I'm also in the process of trying to understand how the tests are done; |
|
As an example, |
Implements Copy-On-Write semantics as an Extension to PRoot. It is supposed to be similar to
cowdancer which doesn't work inside
a proot jail.
This is a naive implementation, intended to get a working version quickly.